process: update metamodel safety analysis#104
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run //src:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
|
@PandaeDo is this ready for review or still in draft? |
7a6985a to
97b50ce
Compare
Ref: closes #102
Ref: closes#102
Ref: closes #102
Ref: closes #102
97b50ce to
30dcf06
Compare
|
@MaximilianSoerenPollak The draft shall show that I still work on it. In aspect to that our remarks are also warm welcome. |
MaximilianSoerenPollak
left a comment
There was a problem hiding this comment.
Some questions & some changes needed.
Any questions let me know.
|
If those things are changed. Here are the resulting errors: folder_templates/features/feature_name/requirements/index.rst:48: WARNING: feat_req__feature_name__some_title: parent need These then also need to be fixed I think. Though that should be us. I'm a bit unsure why it checks 'EXTERNAL' needs here.. that's a bit worrysome. |
Ref: closes #102
Ref: closes #54
Ref: closes #54
Ref: closes #54
Ref: closes #54
Ref: closes #54
There was a problem hiding this comment.
just hint, in this case we would need to check e.g. ASIL B -> QM(B) or ASIL A(B)
masc2023
left a comment
There was a problem hiding this comment.
Fine for now to test, but one comment, in current release we want only ASIL B, not ASIL D, so how can we find ASIL D requirements automatically and let them not be in the code. May needs some discussion
That should be an easy check, just checking if safety is ASIL_D in an requirements. |
aschemmel-tech
left a comment
There was a problem hiding this comment.
See inline comments
There was a problem hiding this comment.
should be "failure_mode"
There was a problem hiding this comment.
This was changed to be consitent accross the types if I remember correctly?
There was a problem hiding this comment.
Aligned to the actual PR it's "fault_models". ](eclipse-score/process_description#54)
There was a problem hiding this comment.
ok, consistent is nice, but according to #54 above the name of the attribute and the content to be written is completely inconsistent: ":violation_cause: "description of failure effect of the fault model on the element"" - the attribute asks for the "cause" and the description is about the "effect"
There was a problem hiding this comment.
I guess we discuss this then tomorrow?
There was a problem hiding this comment.
should start with prefix
There was a problem hiding this comment.
should start with prefix
There was a problem hiding this comment.
^feat_plat_saf_dfa__[0-9a-z_]*$
There was a problem hiding this comment.
should start with prefix
There was a problem hiding this comment.
should start with prefix
There was a problem hiding this comment.
should be "failure_mode"
There was a problem hiding this comment.
should be "failure_effect"
There was a problem hiding this comment.
Aligned to the actual PR it's "fault_models". ](eclipse-score/process_description#54)
There was a problem hiding this comment.
should be "failure_effect"
There was a problem hiding this comment.
After discussion I changed it to violation. If needed we shall discuss it in our round.
There was a problem hiding this comment.
This is the only occurence of "argument" - in the process templates it is in every DFA and FMEA. I am not sure if we discussed to remove this and put the in the description of the "need".
There was a problem hiding this comment.
Argument should be removed as an attribute. It was decided the argument is inside the 'conent
There was a problem hiding this comment.
I missed this one. We deleted it in the metamodel and add a note into the templates in the actual PR that the argument is inside the contend and therefore its mandatory.
MaximilianSoerenPollak
left a comment
There was a problem hiding this comment.
Overall great work, thank you.
Some small comments, requests & questions from my side.
There was a problem hiding this comment.
^feat_plat_saf_dfa__[0-9a-z_]*$
There was a problem hiding this comment.
In this and any of the other new need types.
Are ALL mentioned links & options/attributes mandatory ? Or are some optional?
There was a problem hiding this comment.
Changed the mitigation_issue to optional_links
There was a problem hiding this comment.
This was changed to be consitent accross the types if I remember correctly?
There was a problem hiding this comment.
Argument should be removed as an attribute. It was decided the argument is inside the 'conent
Ref: closes #102
Ref: closes #102
aschemmel-tech
left a comment
There was a problem hiding this comment.
Need to discuss if we want "failure effect" documented at least for FMEA
MaximilianSoerenPollak
left a comment
There was a problem hiding this comment.
Just one more question from me, but I think this is ok.
From my side we can bring this in, depending on the verifies naming status?
There was a problem hiding this comment.
Nitpick:
Should be removed.
This can be done in next PR.
There was a problem hiding this comment.
I think I saw in the process that 'mitigates' can be left empty.
If this is the case, then this should be a optional_link not madatory.
There was a problem hiding this comment.
The mitigation link can be open as long as there is no mitigation (gd_guidl__safety_analysis). To finish a safety analysis a sufficient and linked mitigation is needed.
There was a problem hiding this comment.
That then means though that this should be optional?
There was a problem hiding this comment.
I guess we discuss this then tomorrow?
Ref: closes #102
Ref: closes #102
aschemmel-tech
left a comment
There was a problem hiding this comment.
Ok with merge to enable piloting
aschemmel-tech
left a comment
There was a problem hiding this comment.
Fine for me to merge.
Signed-off-by: Volker Häussler <volker.haeussler@qorix.ai>
* process: update metamodel safety analysis * process: graph_check ASIL update * process: update safety analysis templates * process: update graph check * process: add test cases requirements * process: add checks safety analysis * process: delete ASIL_D option. Add testcases * process: fix test required options * Update ASIL_D check * increase version Ref: closes eclipse-score#102 --------- Signed-off-by: Volker Häussler <volker.haeussler@qorix.ai> Co-authored-by: Sven Bachmann <sven.bachmann.ext@qorix.ai>
Ref: closes #102